Skip to content

*** DNM*** PoC for no wait in multi-pipeline-set-state - #11072

Draft
serhiy-katsyuba-intel wants to merge 5 commits into
thesofproject:mainfrom
serhiy-katsyuba-intel:separate_triggers
Draft

*** DNM*** PoC for no wait in multi-pipeline-set-state#11072
serhiy-katsyuba-intel wants to merge 5 commits into
thesofproject:mainfrom
serhiy-katsyuba-intel:separate_triggers

Conversation

@serhiy-katsyuba-intel

Copy link
Copy Markdown
Contributor

Vibe-coded PoC to sort of revert #8504

Signed-off-by: Serhiy Katsyuba <serhiy.katsyuba@intel.com>
Signed-off-by: Serhiy Katsyuba <serhiy.katsyuba@intel.com>
Signed-off-by: Serhiy Katsyuba <serhiy.katsyuba@intel.com>
Signed-off-by: Serhiy Katsyuba <serhiy.katsyuba@intel.com>
Signed-off-by: Serhiy Katsyuba <serhiy.katsyuba@intel.com>

@kv2019i kv2019i left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks nice a solution to me. Trigger order is kept, 1ms delay is removed and pipeline states still happen at start of LL ticks (= the original reason why trigger processing was delayed to LL thread).

Comment thread posix/include/rtos/task.h
const struct sof_uuid_entry *uid; /**< Uuid */
uint16_t type; /**< type of the task (LL or EDF) */
uint16_t priority; /**< priority of the task (used by LL) */
int16_t priority; /**< priority of the task (used by LL); lower runs first */

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to check do we have a hard limit for max priority (e.g. can we fit max valid priority to a signed 16bit variabe)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants